Repository navigation
switch dependency updates to monthly schedule - #91
Conversation
|
No actionable comments were generated in the recent review. 🎉 📝 WalkthroughWalkthroughRenovate configuration updated: schedule changed from a weekly Wednesday window to a monthly cron ( Changes
Sequence Diagram(s)(omitted — changes are configuration-only and do not add multi-component control flow) Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
renovate.json (1)
8-9: VerifyprHourlyLimit/prConcurrentLimitare sufficient for a monthly cadence.With a 4-hour monthly window and
prHourlyLimit: 2, Renovate can create at most 8 PRs per monthly run. Any excess PRs will be deferred until the next month, assuming the scheduled window has passed by the time earlier PRs are merged/closed.
group:allNonMajorcollapses non-major updates into a single PR, and major updates are gated behinddependencyDashboardApproval, so this is unlikely to be an issue in practice — but worth confirming if the repository has a high count of major-version updates that could pile up.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@renovate.json` around lines 8 - 9, Confirm that the current Renovate rate limits are adequate for a 4-hour monthly scheduled run: review prHourlyLimit and prConcurrentLimit and increase them if you need more than 8 PRs per run (prHourlyLimit: 2 × 4 hours = 8 PRs). Check how many potential PRs could be produced given your dependency graph and the config entries group:allNonMajor and dependencyDashboardApproval (non-majors collapse, majors need approval) and adjust prHourlyLimit and/or prConcurrentLimit upward to accommodate peak monthly churn so excess updates are not deferred to the next month.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@renovate.json`:
- Line 6: The Renovate config uses the deprecated later.js natural-language
schedule string under the "schedule" key; replace that human-readable value with
a cron expression or preset: update the "schedule" entry in renovate.json to use
the cron form "* 0-3 1 * *" (or the "schedule:monthly" preset) so Renovate uses
the supported cron syntax instead of the later.js text format.
---
Nitpick comments:
In `@renovate.json`:
- Around line 8-9: Confirm that the current Renovate rate limits are adequate
for a 4-hour monthly scheduled run: review prHourlyLimit and prConcurrentLimit
and increase them if you need more than 8 PRs per run (prHourlyLimit: 2 × 4
hours = 8 PRs). Check how many potential PRs could be produced given your
dependency graph and the config entries group:allNonMajor and
dependencyDashboardApproval (non-majors collapse, majors need approval) and
adjust prHourlyLimit and/or prConcurrentLimit upward to accommodate peak monthly
churn so excess updates are not deferred to the next month.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@renovate.json`:
- Around line 6-7: The JSON is invalid because the "schedule" property line is
missing a trailing comma, which breaks parsing and prevents the
"dependencyDashboard" setting from being applied; fix by adding a comma after
the "schedule": ["* 0-3 1 * *"] entry so the "dependencyDashboard" key is a
valid subsequent property (check the renovate.json object containing "schedule"
and "dependencyDashboard" and ensure proper comma separation between entries).
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Summary by CodeRabbit